fix(aws-lambda): skipped capturing browser-generated asset requests #2091
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
The Lambda Function URL creates an entry span for all requests handled by the Lambda, including 404 or asset calls (e.g., favicon.ico). This is same as collector, Instana traces all incoming requests by default. I'm closing this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added logic to detect and skip tracing for asset-related requests based on the request path.
Details:
Introduced a check to identify browser-generated asset requests (e.g., images, CSS, JS, source maps, etc.).
If the request path matches any of these extensions, the span is skipped to reduce unnecessary tracing noise.
refs https://jsw.ibm.com/browse/INSTA-48358